![]() VS Code sets this up automatically as a workspace. Why is that?ĭocker supports mapping a directory on your computer (the host) so that it’s accessible within the container’s file system. If you followed the setup steps in part two of this series, and your application uses SQLite as a database, you may have observed the app just working in the Rails console or in your browser. Even though it’s the simplest, and may even appear to just work without a lot of extra setup, understanding why it appears that way introduces some fundamentally important things to understand about container functionality that VS Code and Remote-Container have set up for us. Here, I’ll cover setting up SQLite for a Rails dev container in Visual Studio Code. Instead, I’m going to break it down over multiple posts. I’d originally planned to cover the three most common SQL-based databases in a single post, but covering the details and differences of container-based Postgres, MySQL, and SQLite setups in such a way proved to be a little too sprawling for my tastes. So for my next batch of experiments, I explored what’s required to add database support to the development container. ![]() That’s great progress and all, but I’ve never worked on a real, production Rails app that didn’t rely on a database of some kind. In my previous experiment, I showed how I got a mature (that is, pre-existing) Rails app to boot in a Visual Studio Code devcontainer, leaning on the default configuration provided by VS Code’s Remote-Container extension.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |