HEY

I'm remaking witches.academy, and I'm stuck at bundle exec rake secret.

It's super not working and I'm stuck >.>

My error says package configuration for protobuf is not found

Also, this keeps popping up?

An error occurred while installing cld3 (3.1.2), and Bundler cannot
continue.
Make sure that `gem install cld3 -v '3.1.2'` succeeds before bundling.

@sendoshin

Any ideas?

@spiderrobotpig Using Nanobox, or ...?

@sendoshin Apparently I could just do a native install in Digital Ocean and my account is still good so I did it there.

Currently working from this: https://anystack.xyz/how-to-install-mastodon-ubuntu/

@spiderrobotpig Yeah, it was added as a dependency when language detection was upgraded a few versions back. Took me a while to figure everything out to make that work properly so that Nanobox could handle it automatically.

So the first step is you have to actually install protobuf using the system package manager. Assuming Ubuntu, `sudo apt-get install protobuf-compiler` should pull in everything you need.

@sendoshin It says that package config isn't found, but that the package is installed.

Bluh I forget how frustrating this can get >.<

@spiderrobotpig Yeah, it's pretty much a nightmare managing Ruby dependencies, especially if there are any binaries involved.

So, basically it's trying to build its own version of a library called CLD3, which is the language detection library used in Chrome. It has to build its own because the normal version depends on Chrome itself, and that's just way too much for most uses.

But. It needs help to find the other things it still depends on...

@sendoshin Makes sense. No idea how to fix it though?

Because I've installed the package and the dependencies both with root and the mastodon user and for some reason bundle install can't find them

@spiderrobotpig It's honestly been nearly two months since I tackled this myself, so ... I'm trying to remember all the details... Sorry for the delays.

@sendoshin No worries. I appreciate the help.

If it's too much I'm sure I can figure it out at some point

@spiderrobotpig So, for some reason it's having trouble finding one of the libraries it needs. I'm trying to remember which ones it depends on, other than protobuf. Because there was at least one it didn't actually have a way to detect and warn about in the build process itself...

I wanna say it's zlib? `sudo apt-get install zlib1g`? I mean, that's usually already installed, but I guess you never know...

@sendoshin Yeah it's already there.

Bluuuuuuuuuuh

I guess I'll just wait until I can get $10 up and use nanobox this is bullshit

@spiderrobotpig I can zap you the $10 if you like... I think you get like 20 days free, though, so ... up to you.

@sendoshin Oh yeah, you're right.

KK I'm gonna do that how awful is this gonna be?

@spiderrobotpig Not awful at all, in my experience. I documented the process in the official docs, but I have a much more detailed walkthrough on the Nanobox blog that I highly recommend, especially for the bits about managing it once it's up.

@sendoshin Link plz? haha

@spiderrobotpig 😂

https://content.nanobox.io/getting-social-with-mastodon-and-nanobox

@sendoshin Oh god this looks so much more complicated >^<

@spiderrobotpig Skip the bit about what I did to make it work. It's a lot less intimidating than you think.

@spiderrobotpig Ah, whoops. You can just re-use those values from when you set it up the first time. You'll want to import your database contents anyway, if they're still around, so there will be an extra step or two not in that doc.

Alternately, if you're starting over from nothing completely, you can just clone the Mastodon repo on your computer and run it in that directory. All Nanobox commands are meant to be run in the root folder of your project.

@sendoshin I'm so confused now >.<

@spiderrobotpig Sorry. The values you're setting in the dashboard are the same values you would have set in the .env file manually. So you can take the values from your existing .env file on DO and just use them, here.

@sendoshin I honestly have no idea what you're asking me to do now tbh

Like, I don't understand how this is supposed to work at all apparently.

@spiderrobotpig Hrm. How to reword...

So, you already have a Mastodon instance running on DO, right?

@sendoshin No, that's the problem. I can't get it running because that awful fucking update

@spiderrobotpig OK, not running, then. Installed? It sounded like it was at least running at one point...

@sendoshin It was at some point, but it's not now. The droplet got deleted

@spiderrobotpig Ah. OK. So you have to regenerate the secrets. Gotcha.

In that case. What OS are you running on your computer?

@sendoshin I'm on windows rn

@spiderrobotpig Alright, do you use git there much?

@sendoshin A little bit? I'm using the app at the moment, and I have a program where I can SSH into the droplets

@spiderrobotpig OK, cool. We don't need to access the droplets at all, really.

So we're gonna need to clone the Mastodon repo from GitHub onto your computer. Not sure which app you use for that, but it should work fine with https://github.com/tootsuite/mastodon as the origin URL.

@spiderrobotpig (Argh. Masto "helpfully" dropped the https part...)

@sendoshin I already have a Mastondon repo on here

@spiderrobotpig Oh, even better. Forget I said anything about cloning it. :D

@sendoshin Oki. Copying over the variables from the old .env.production at the moment

@spiderrobotpig Ah, perfect. That's the one I meant, even!

@sendoshin But I still don't understand where I'm supposed to be running these things. Because I can't get bundle install to work on the droplet

@spiderrobotpig Right. You won't interact with the droplet directly at all. Nanobox will do that for you.

@sendoshin OKay, but I need to generate the secrets and you said there's something else I need to run?

git checkout $(git tag | tail -n 1)

@spiderrobotpig Nah, you already generated the secrets. I need to update that article for migrating from other places.

As to that git command, it just makes sure you're using the latest tagged version. You've probably done that manually already.

@sendoshin I didn't generate the secrets though, remember? That was the whole reason I tagged you in

@sendoshin The secrets wouldn't generate because bundle install won't work cos that bullshit update

@spiderrobotpig Right, but you copied the old ones from your old .env.production, and they should work just fine.

@sendoshin No I didn't have them there. That was the one I was working on

@spiderrobotpig Ah. Well, then, we can generate them next. You'll need to be in the command prompt I mentioned earlier far that, too.

@sendoshin Trying.

Powershell isn't letting me change directory I swear to fucking god right now

@spiderrobotpig ..... Wow. Way to go Windows?

@sendoshin Managed it in CMD.

Okay, thanks again for all of this. What do I do next?

@spiderrobotpig Oh, sorry, I was trying to update the article a bit as we went along.

If you have Nanobox installed, you should be able to run that command to generate the secrets right from there.

@sendoshin From where? I don't know what you mean when you say that

@spiderrobotpig It would have been typed into CMD.

@sendoshin bundle install wouldn't work in CMD

@spiderrobotpig Which is why it would have been `nanobox run bundle exec (etc)` instead...

@sendoshin Bluh >.<

I'm so close to crying at this point.

@spiderrobotpig Yeah. I'll just stop. Sorry.