| #!/bin/bash | |
| # Globals | |
| TIMESTAMP=$(date +%s) | |
| MOUNT_DIR="/mnt" | |
| BASE_MOUNT_DIR="$MOUNT_DIR/image_$TIMESTAMP" | |
| MOUNT_IMAGE="" | |
| # Usage declaration | |
| display_usage() { |
| #!/bin/bash | |
| USAGE="\n\x1b[31mUsage:\x1b[0m extract_table_from_mysql_dump.sh my_table /path/to/dump.sql\n\x1b[32mOptional 3rd parameter:\x1b[0m /path/to/export/to\nThe export filename will default to extracted_{my_table}.sql\n" | |
| if [[ -z "$1" ]] ; then | |
| printf "$USAGE" | |
| exit 1 | |
| fi | |
| # Check the table name was provided | |
| if [[ -z "$2" ]] ; then |
For security reasons, you should probably grant select, delete, update and insert to your app user in production.
Have another user who can do alter, create, drop and index when running migrations.
If you run seeders in production, also grant select, insert and references to the migration user.
Yeah, 2 users, migrations are not always run in production everyday and this keeps more secure your database.
So, with credit to the Factorio wiki and cbednarski's helpful gist, I managed to eventually setup a Factorio headless server. Although, I thought the process could be nailed down/simplified to be a bit more 'tutorialised' and also to document how I got it all working for my future records.
The specific distro/version I'm using for this guide being Ubuntu Server 16.04.1 LTS. Although, that shouldn't matter, as long as your distro supports systemd (just for this guide, not a Factorio headless requirement, although most distros use it as standard now).
The version of Factorio I shall be using is 0.14.20, although should work for any version of Factorio 0.14.12 and higher.
If you prefer a simple, automated setup, [Bisa has a really handy init script that will do most of the work for
