last day (19 days later) » 

20:03
Here begins the chronicle of my flailing around trying to set up metasmoke on Thomas Ward's graciously-donated server space...
This'll be part documentation, part humor, part mockery of my past self
1. Setting up MariaDB
Old server version: mysql Ver 15.1 Distrib 10.3.12-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
New one:
mysql Ver 15.1 Distrib 10.1.43-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
Looks compatible
Running the backup script on old SQL instance to get a new DB copy
(Will do this again right before cutover)
Making a new DB user for metasmoke in Maria
... and looking up the syntax like I do EVERY TIME
MariaDB user is metasmoke/metasmoke
because why not
Importing new DB
(just mysql < file.sql)
Installing RVM, the best thing since sliced bread
... maybe excluding cinnamon rolls
We're currently on Ruby 2.5.0, gonna keep that for now
lol somehow no binary rubies found
so it's gonna compile it
(which is fine, just takes a minute or so longer)
okay so that didn't work; I guess we're going to 2.5.7
(which has a binary ruby available)
and done
also my laptop is at 70% and I left my charger at home
so it's a race against the clock
SUSPENSE!
aaaaand now I forgot what comes next
oh cap deployments
okay now the fun part
Gonna just write out all the error messages and all the fixes
SSHKit::Runner::ExecuteError: Exception while executing as [email protected]: ruby exit status: 2
ruby stdout: Nothing written
ruby stderr: Gemset 'metasmoke' does not exist, 'rvm ruby-2.5.7 do rvm gemset create metasmoke' first, or append '--create'.
(Do what it says, rvm ruby-2.5.7 do rvm gemset create metasmoke)
Cap does the initial git clone
complains because (of course) config files don't exist yet
but it creates the whole dir structure
00:03 deploy:check:make_linked_dirs
      01 mkdir -p /var/railsapps/metasmoke/shared/config
    ✔ 01 [email protected] 0.397s
00:04 deploy:check:linked_files
      ERROR linked file /var/railsapps/metasmoke/shared/config/database.yml doe…
^ Looks like that
20:46
Capistrano got to bundle install
And threw the ye-olden error I hit every. single. time
An error occurred while installing mysql2 (0.5.2), and Bundler cannot continue.
Make sure that `gem install mysql2 -v '0.5.2' --source 'https://rubygems.org/'`
succeeds before bundling.
HAH
SOMEONE FORGOT THEIR SUDO PASSWORD ALREADY
... oh
wrong machine
that's why
okay it works
if you use the right terminal
So it's just sudo apt install libmysqlclient-dev for that
Next:
 DEBUG [fe7572a1] 	rake aborted!

ExecJS::RuntimeUnavailable: Could not find a JavaScript runtime. See github.com/rails/execjs for a list of available runtimes.
Should just be sudo apt install nodejs for that one
@Undo go to latest node
don't use straight sudo
otherwise it installs 0.10.2 (old)
want me to install up-to-date nodejs?
Sure
1 moment
I feel like I've gone down this road and latest broke something, but probably wrong
Or was a long time ago and they've fixed it
sudo apt-get install curl
curl -sL deb.nodesource.com/setup_13.x | sudo -E bash -
sudo apt-get install nodejs build-essential
nodejs 13 should be installed now see if it works @Undo
if not i'll uninstall and we can put to the old one :)
21:10
Sweet, trying it now
Seems okayish so far
noms cake and stands by for breakages
workarounds dictate yarn upgrade give me a second to install yarn
Already there
Got a weird reproducibility issue
21:23
Happens in Cap, not when running manually
okay actually I have to set up redis first
otherwise it's irritating
in Charcoal HQ, 7 secs ago, by Undo
@thesecretmaster Do you have a Redis setup guide somewhere? Moving servers, need to know how to get it working w/ custom additions and such.
Basically blocked on that for now

  last day (19 days later) »