Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DevOps and Readerself, automating deployment. #86

Open
rvalle opened this issue Jan 17, 2017 · 5 comments
Open

DevOps and Readerself, automating deployment. #86

rvalle opened this issue Jan 17, 2017 · 5 comments

Comments

@rvalle
Copy link

rvalle commented Jan 17, 2017

I am experimenting to automated the deployment of readerself with puppet.

I can install/configure the LAMP software stack, the readerself distribution and create the configuration files:

database.php
readerself_config.php

From parameters configured in puppet / yaml files

However readerself will not create the database structure on start, but instead fail. It wont enter the setup either on first run.

I am not sure what the criteria is for launching the setup process.

Is there anyway to force-create the database structure?

I also noticed that there are some settings stored in the DB vs configuration files. It would be desirable to have defaults from config files as they are easier to automate.

Same goes for LDAP base roles. would be nice to specify an LDAP group for the administators.

@stephanediondev
Copy link
Owner

You can't reach the setup page if the file readerself_config.php is already created, or precisely if the key "salt_password" exists in this file

I suggest you have a look to the Symfony version of this application (but there is no LDAP support). It wiil be easier to make a deployment script https://github.com/readerself/readerself-symfony

@rvalle
Copy link
Author

rvalle commented Jan 18, 2017 via email

@stephanediondev
Copy link
Owner

I made a commit on the readerself-symfony version, LDAP is implemented

new parameters

ldap_enabled: false
ldap_server: 'ldap://localhost'
ldap_port: 389
ldap_protocol: 3
ldap_rootdn: 'cn=Manager,dc=my-domain,dc=com'
ldap_rootpw: 'secret'
ldap_basedn: 'dc=my-domain,dc=com'
ldap_search_user: 'mail=[email]'
ldap_search_group_admin: 'cn=admingroup'

@rvalle
Copy link
Author

rvalle commented Jan 23, 2017

thanks! I will definitely switch.
is the DB compatible?

@stephanediondev
Copy link
Owner

No, it's a new fresh database with innodb, utf8mb4, foreign keys ..

I made 2 commands to import all items and starred items
It can be heavy if you have a lot of items on your old installation

bin/console readerself:migration:all-items
bin/console readerself:migration:starred-items

In parameters you must set database_*_old to connect to the old version

And the users are not imported yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants