angular-fullstack/generator-angular-fullstack

openshift during setup

Open

#1.598 aberto em 2 de fev. de 2016

Ver no GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (6.134 stars) (1.268 forks)batch import
Help Wantedinvestigate

Description

Would it be nice and convenient to ask where the application will be deployed? For example if you decide to deploy it on openshift, it is absolute necessary to set the openshift server as production so you do not have npm installing all dev packages which causes openshift to run out of inodes and diskspace.

grtz

Guia do colaborador

Pilha de tecnologia
javascriptexpressnodejsangular
Domain
devops
Tipo Issue
feature
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-3 hours
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
stale
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
needs investigation
Prerequisites
Basic knowledge of Yeoman generators
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
40
Direção de pesquisa
The issue requests adding a prompt during setup to ask about the deployment target (e.g., OpenShift) to automatically set production mode and avoid installing dev dependencies. To implement, examine the generator's prompt files (likely in the `app` or `component` subdirectory) and identify where deployment questions are asked. Look at existing prompts for environment settings. The generator uses Yeoman's `this.prompt()` method; you would add a new question to capture whether the user plans to deploy on OpenShift and then conditionally set the NODE ENV or modify the generated configuration accordingly. Since the issue is old and no comments confirm maintainer interest, it may be wise to first ask for clarification on the desired implementation.