Credentials

Project credentials

Default development credentials:

account	username	password
mysql	admin	testing_password
dashboard	admin	testing_password

Changing the credentials is a bit hassle right now but hopefully it will get easier with some refactoring. admin application user inside dashboard. database can be accessed through phpmyadmin using mysql credentials.

mysql user account

This account is used by the application to access the database. In development it is granted all privileges and can be used by developer for looking into the database. Credentials are stored inside /.env file in the root of the repository. Use /.env.example file for reference. Mysql needs to grant permissions to a particular database as well. That is done inside /docker/db/init/database.sql file.

1. start the containers.
2. navigate to user accounts -> edit privileges -> login information. Update username and password and click "go".
3. go back to user accounts and click export on newly updated user. You should get a line similar to this:

GRANT ALL PRIVILEGES ON *.* TO `new_username`@`%` IDENTIFIED BY PASSWORD 'HASHEDPASSWORDSTRING' WITH GRANT OPTION;

Replace correct line in /docker/db/init/database.sql. 4. Update .env file with updated credentials. 5. delete db storage and recreate the container

application user

The only application user that is created in the development is the admin user. It's credentials are stored as a row in the database in /docker/db/init/database.sql file.

1. start the containers
2. log into the admin interface and click on change password
3. (optional) log into phpmyadmin and look at the users table inside svommer_web database. Copy username and passwd fields over to /docker/db/init/database.sql file if you want those credentials to persist even after the containers has been rebuilt. That like looks like this:

INSERT INTO `users` (`username`, `passwd`, `name`, `last_password`, `role`) VALUES
('some_custom_username', 'HASHEDPASSWORD', 'Administrator', NOW(), 1);

API keys

Stripe

Stripe is a e-commerce service for processing payments. Take a look at their documentation on how to get yours. API keys are not necessary if you don't plan on testing the store so filling in some random strings inside .env file should work just fine. Stripe uses signing keys for web hooks. They are printed inside the logs from the stripe container if you provide correct keys inside .env file. Check the logs by running docker-compose logs stripe