Hello! After spending many development hours in my past years running on Virtualbox/Vagrant-style setups, I've decided to take the plunge into learning Docker, and after getting a few containers working, I'm now looking to figure out how to deploy this to production. I'm not a DevOps or infrastructure guy, my bread and butter is software, and although I've become significantly better at deploying & provisioning Linux VPS's, I'm still not entirely confident in my ability to deploy & manage such systems at scale and in production. But, I am now close to running my own business, so these requirements are suddenly going from "nice to have" to "critical".

As I mentioned, in the past when I've previously developed applications that have been pushed onto the web, I've tended to develop on my local machine, often with no specific configuration environment. If I did use an environment, it'd often be a Vagrant VM instance. From here, I'd push to GitHub, then from my VPS, pull down the changes, run any deployment scripts (recompile, restart nginx, etc), and I'm done.

I guess what I'm after with Docker is something that's more consistent between dev, testing, & prod, and is also more hands off in the deployment process. Yet, what I'm currently developing still does have differing configuration needs between dev and prod. For example, I'd like to use a hosted DB solution such as DigitalOcean Managed Databases in production, yet I'm totally fine using a Docker container for MySQL for local development. Is something like this possible? Does anyone have any recommendations around how to accomplish this, any do's and dont's, or any catches that are worth mentioning?

How about automating deployment from GitHub to production? I've never touched any CI/CD tools in my life, yet I know it's a hugely important part of the process when dealing with software in production, especially software that has clients dependent on it to function. Does anything specifically work well with Docker? Or GitHub? Ideally I want to be avoiding manual processes where I have to ssh in, and pull down the latest changes, half-remembering the commands I need to write to recompile and run the application again.

My title sucks, couldn't word it better.

So, I hate having to use the tilde char. Doing tildes.net~tildes is much harder for me than tildes.net/t/tildes. It would be cool if tildes also supported using "/t/". I am not suggesting to remove the "~", but make one redirect to the other.

Looking at the development setup page, the suggested setup is to use vagrant to create and provision a VM. Out of curiosity, is there a reason for this preference over setting up a Tildes Docker image inside the repo? Tildes seems like a pretty simple and straightforward web app, it shouldn't be difficult to create. Is it just a developer preference of Deimos/Tildes devs? Or is there a logistical reason?

Pretty straight forward question, but basically I was watching a discussion panel the other day talking about the ethics of Self-Driving cars. A topic came up about people writing crappy code, and more than that, people not testing their code. And if they do, they do point testing. I am in my last semester of uni and I am working with some companies where we are doing pretty extensive testing, happy flows and a lot of alternate flows, as well as UI/UX testing. I wanted to extend this question to you, do you guys do testing, what type? How much do you focus on it? And if u love it/hate it?

I wasn’t able to find a discussion on this, though I’m sure there has been, and for that, I apologize.

Is there any kind of timeframe on the release of a mobile app for tildes?

I would guess that on Reddit most of their traffic comes from people accessing the site on their phones at this point, but I could be wrong. In any case, it certainly is a large portion of the users that access the site in this way.

With that in mind, it would be nice to be able to access tildes from a mobile app to do away with the clunkiness that comes with using the site through a mobile browser. I don’t mean to sound like it’s terrible. The site functions well enough through a mobile browser, but it would certainly have me using tildes a lot more if the convenience of a mobile app was available.

I’m sure the developers are very busy, and I don’t want to sound demanding, I’m just curious.

And once again, I apologize if this has been discussed recently.

A couple of years ago I had the itch for a 3D platformer and didn't feel like replaying Super Mario 64 for the nth time. I saw that there was a game called Poi and it was clearly inspired by SM64. I picked it up and played it while it was in early access.

I enjoyed my time with it, but because the game wasn't content and feature complete, I ended up making my way through an unfinished, buggy version. This is not a complaint, as I knew well that it was still in development, but I can't deny that it hampered my enjoyment of the final product. When I finally sat down to play through the game for the "first" time after its release, my previous experience soured my current one because I was retreading familiar, albeit improved, levels.

Distance, another early access game I purchased, released in full this past month. Unlike with Poi, I actually stopped myself from playing Distance in early access (after trying it out briefly), so that I wouldn't ruin the game for myself. As such, my enjoyment of it has been far greater. Those two games, plus a handful of others, have made it such that I pretty much will no longer buy a game if it's in early access, simply because I'd rather wait for the full thing.

With that in mind, I'm curious if other people do the same thing, or if some people actually like the behind the scenes experience of playing a game as it gets built? Also, what are some early access success stories that have had solid, full releases? What are some that would be considered successes in spite of the fact that they haven't fully released yet?