Open bradtaniguchi opened 4 years ago
Checking it out now!
It seems they only offer MySQL or PostgreSQL, which since this module and the underlying mssql
module rely on the database being MS SQL is an issue. Let me do a little research/give it some thought on how to best go about this. Perhaps its time for me to look into Docker....
For the discord-bot someone contributed to the bot development configuration by adding a mongodb installation via a Dockerfile installation here: https://github.com/freeCodeCamp/discord-bot/blob/1fc2d9c2381abfe946ea4119e4d8420accb4fbb6/.gitpod.Dockerfile
Probably could be changed a bit to loadup an mssql installation instead :)
edit added permalink incase the file gets deleted.
Looking into this a bit more, I think we might be able to get MS SQL Express for Linux going for this. Going to spend a bit of time on it here and there to see if it will be viable.
I was going over the issues and came back to this one.
Things have changed since creating this issue, with the main thing being github has its own codespace feature. There are repos out there that showcase how to get a microsoft sql instance, such as this one: https://github.com/microsoft/vscode-remote-try-sqlserver
It might make more sense, and be easier to test out a codespace than gitpod. (gitpod has changed dramatically as well, but there should be a good overlap with all the microsoft products)
Will update the title accordingly.
I took a look at the above repo, looks like it relies on docker-compose + Dockerfile for a custom environment+db service. I might either utilize a near carbon-copy setup moved over from there, or use a cut-down version using docker-compose to get a database instance.
Good learnings for sure though, as its been a while since I've looked at ops stuff.
So there is a gitpod setup in the repo right now, I'm not sure if it works though.
Will look into this as a basis for codespace development.
So one of the slightly annoying aspects of testing out this plugin is the fact you need an mssql installation locally and some "hooking it up" logic. One way to get around this is to use something like gitpod which is free for open source, to get a ready to go dev environment that could also be setup with the mssql installation.
This would allow anyone to try out this plugin without much work. Might be worth looking into so its easier to mess around with the plugin, especially if we are to continue updating it :)