gina 0.1.5-alpha.2 → 0.1.6-alpha.2

package/README.md

@@ -1,6 +1,6 @@
-# Gina
+# Gina <img src="https://gina.io/favicon-16x16.png"  alt="Gina icon" style="position: absolute; top:10px; margin-right: 10px;" />
 
-[![GitHub version](https://badge.fury.io/gh/Rhinostone%2Fgina.svg)](https://badge.fury.io/gh/Rhinostone%2Fgina) [![npm version](https://badge.fury.io/js/gina.svg)](https://badge.fury.io/js/gina) [![node version](https://badge.fury.io/node/v/gina.svg)](https://badge.fury.io/node/v/gina)
+[![GitHub version](https://badge.fury.io/gh/Rhinostone%2Fgina.svg)](https://badge.fury.io/gh/Rhinostone%2Fgina) [![npm version](https://badge.fury.io/js/gina.svg)](https://badge.fury.io/js/gina) 
 
 <strong>Gina I/O</strong> - Node.js MVC and Event Driven framework
 
@@ -32,7 +32,7 @@ Gina aims to be at the same time a framework, a deployment and monitoring enviro
 
 | versions | description |
 |--------|--------|
-| alpha       | Preview release: ==not recomanded for production==      |
+| alpha       | Preview release: <mark>not recomanded for production</mark>      |
 | latest       | Latest stable relase        |
 
 #### 1st method (prefered) - Custom PREFIX
@@ -127,6 +127,7 @@ By starting the framework, you will also start the server.
 ``` tty
 gina start
 ```
+
 __NB.:__ This is an alias for `gina framework:start`
 
 
@@ -136,7 +137,7 @@ A project is a collection of bundles (applicaitons or services). See it as a rep
 Let's create our first project and install Gina.
 
 ```tty
-cd ~/.Sites
+cd ~/Sites
 ```
 
 
@@ -154,6 +155,7 @@ gina project:add @myproject
 ```
 
 If you need to remove this project later
+
 ```  tty
 gina project:rm @myproject
 ```
@@ -172,11 +174,16 @@ Ok ! Let's do it !
 ``` tty
 gina bundle:add frontend @myproject
 ```
+
 __NB.:__ If you are launching the command from the project directory, you don't need to add `@myproject`. The same goes for all bundles commands.
 
 We have just created a frontend application that will host our homepage.
 You will find all bundle sources under `myproject/src`.
 
+__Important:__ Since you are not running a local DNS Server, you have to change the host informations. Go to `myproject/env.json` & replace `dev` hostname from `frontend-{env}-{scope}-v{projectVersionMajor}.{rootDomain}` to `localhost`.
+This is a tempory hack and gina will soon be provided with its own local DNS Server
+
+
 You can start the bundle with the following command:
 
 ```tty
@@ -191,7 +198,7 @@ gina bundle:start frontend @myproject
 > ```
 
 
-Now, visit http://127.0.0.1:3100/  to check your homepage.
+Now, visit http://localhost:3100/  to check your homepage.
 Isn't it sexy !?
 
 If you need to stop your bundle
@@ -200,6 +207,7 @@ gina bundle:stop frontend @myproject
 ```
 
 If you need to restart you bundle
+
 ```tty
 gina bundle:restart frontend @myproject
 ```
@@ -213,7 +221,9 @@ Let's add a view on our frontend
 ```tty
 gina view:add frontend @myproject
 ```
+
 Then restart your bundle
+
 ```tty
 gina bundle:restart frontend @myproject
 ```
@@ -243,17 +253,19 @@ You can check which are the environments set for your projects
 ```tty
 gina env:list
 ```
+
 __or for a particular project__
+
 ```tty
 gina env:list @myproject
 ```
 
-__NB.:__ when adding an environement, you will do so for the entire project.
+__NB.:__ When adding an environement, you will do so for the entire project.
 
 #### Setting your application starting environment on runtime
 > This method does not memorize the selected environment as the default one for your application
 
-You can have multiple environments for your project and decide to pick one as the starting env by using `--env=your_env` every time you have to run a bundle.
+You can have multiple environments for your project and decide to pick one as the starting env by using `--env=<your_env>` every time you have to run a bundle.
 
 ```tty
 gina bundle:start frontend @myproject --env=prod
@@ -263,32 +275,45 @@ __NB.:__ Omitting `--env=<env>` will fallback to your project default environmen
 #### Setting your project or your application default environment
 
 For the entire project & for all bundles inside by default
+
 ```tty
 gina env:use prod @myproject
 ```
+
 __NB.:__ If you need to change it for a particular bundle, you still can do it at runtime using `--env=<your env>` to override the default settings. This will not set `<your env>`as the default environment for the whole project.
 
+__Attention:__ None-development `env` must be built before starting or restarting the bundle
+
+```tty
+gina project:build prod @myproject
+```
 
 
 #### Other operations you can apply to your environment:
+
 __Adding a new environment for your project__
+
 ```tty
 gina env:add staging @myproject
 ```
+
 __Removing an existing environment for your project__
+
 ```tty
 gina env:rm staging @myproject
 ```
 
 __Defining an existing environment as `development` (you can only have one like this)__
+
 ```tty
 gina env:link-dev <your new dev env>
 ```
 
 __Benefits from using a `development` environment__
+
 You will not have to restart your bundle anytime you modify files inside directories like :
 - /controllers
-- /piblic
+- /public
 - /templates
 
 ### Region
@@ -331,7 +356,7 @@ So to handle log storage for your application, you have 2 options: see 2nd & 3rd
 
 __2nd Method - Old school way__
 
-> __Attention: __ You will have to handle yourself [log rotation](https://linux.die.net/man/8/logrotate)
+> With this method, you will have to handle yourself [log rotation](https://linux.die.net/man/8/logrotate)
 
 ```tty
 gina bundle:start frontend @myproject --log > /usr/local/var/log/gina/frontend.myproject.app.log 2>&1
@@ -356,7 +381,7 @@ You might need to restart the gina :
 gina restart
 ```
 
-__NB.: __For development purposes, using the CLI `gina tail` is still a better option because you will have a better overview of what is really going on for all your application at once & for the framework.
+__NB.:__ For development purposes, using the CLI `gina tail` is still a better option because you will have a better overview of what is really going on for all your application at once & for the framework.
 
 #### Setting default log level
 
@@ -381,7 +406,7 @@ gina framework:set --log-level=debug
 ### Installing a certificate
 
 > __Attention__
-> ==One certificate per bundle/service==
+> <mark>One certificate per bundle/service</mark>
 
 You now want to install a certificate for your project in order to run your project with HTTPS scheme or with HTTP/2 protocol ?
 At this moment, Gina does not generate a cetificate for you, but you can use a service like [sslforfree](https://www.sslforfree.com) to genreate a free 90 days certificate, then install it into your Gina home directory depending on the scope of your host (targeted machine: local or production).

package/framework/v0.1.6-alpha.2/VERSION

@@ -0,0 +1 @@
+0.1.6-alpha.2

package/framework/v0.1.6-alpha.2/core/asset/plugin/dist/vendor/gina/css/gina.min.css.map

@@ -0,0 +1 @@
+{"version":3,"sources":[],"names":[],"mappings":"","file":"/usr/local/lib/node_modules/gina/framework/v0.1.6-alpha.2/core/asset/plugin/dist/vendor/gina/css/gina.min.css","sourcesContent":[]}