Skip to content

Maria db #30

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

Merged
merged 4 commits into from
Sep 21, 2017
Merged

Maria db #30

merged 4 commits into from
Sep 21, 2017

Conversation

reactivepixel
Copy link
Owner

@jonathandavidpollock Please review this Pull Request (PR). It needs to be verified as viable. To obtain this branch you need to download it locally and run it with the following commands.

Ensure you are not currently running mysql on port 3306 locally as that port will be bound and used by this process.

git fetch origin
git checkout mariaDB

# Dispose of previous containers and volumes an rebuild
docker-compose down -v && docker-compose up --build

To verify this works please open up Sequel Pro and open a connection with the following information and check to see that the database max has a table Members with 1 row

host: 127.0.0.1
user: root
pass: down_and_dirty_deeds
port: 3306
database: max

If you can verify this, the PR is good to merge and it closes #25 which has info on how to interact with the database which is needed for #28

@mykahT18
Copy link
Contributor

@jonathandavidpollock @reactivepixel
I have pulled this down and ran it. Everything is working there is a user in that database.

@mykahT18 mykahT18 self-assigned this Sep 21, 2017
@mykahT18 mykahT18 merged commit bc0f6c4 into dev Sep 21, 2017
@reactivepixel reactivepixel deleted the mariaDB branch September 22, 2017 15:34
@reactivepixel reactivepixel restored the mariaDB branch September 22, 2017 15:34
@reactivepixel reactivepixel deleted the mariaDB branch October 27, 2017 14:35
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

Successfully merging this pull request may close these issues.

Create DB
2 participants