noosfero | Stable docker configurations for linux (!1386)

Luan Guimarães gitlab at mg.gitlab.com
Thu Jan 25 15:28:58 BRST 2018


New Merge Request !1386

https://gitlab.com/noosfero/noosfero/merge_requests/1386

Project:Branches: luanguimaraesla/noosfero:compose to noosfero/noosfero:master
Author:    Luan Guimarães
Assignee:  

### New docker-compose behavior
Now the configuration is setup to run two containers, one with postgres and the other with noosfero. There are two options, development and production mode.
- Development:  
```
docker-compose -f dev.yml up --build
```
This configuration synchronize noosfero local repository with the code into the container. You'll be able to edit the code outside the docker container.  
You still able to use bash and other commands inside the container. After it is running, type the command:  
```
docker-compose -f dev.yml exec noosfero bash
```
You can access the web interface at `http://localhost:3000`

- Production:
```
docker-compose -f prod.yml up --build
```
Before you run this command be aware that there are default database credentials in the `prod.yml` file. So, for several security reasons the user should change it locally in both yml sections `postgres` and `noosfero`. Everything else is done automatically and the user will be able to access the production server at `http://localhost`

#### Broken symlinks
Some broken symlinks related on #300 were removed. It causes some failures when docker is trying to build the image of noosfero.

#### OSX configuration
Some OSX configurations for docker must be outdated now.


---
Reply to this email directly or view it on GitLab: https://gitlab.com/noosfero/noosfero/merge_requests/1386
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listas.softwarelivre.org/pipermail/noosfero-dev/attachments/20180125/4d07869c/attachment.html>


More information about the Noosfero-dev mailing list