nvim-lspinstall VS Packer

A word of caution, I believe lspinstall has been deprecated in favor of nvim-lspinstall which itself has also been deprecated in favor of mason-lspconfig

kabouzeid/nvim-lspinstall will aide in installing lsp's if you want. I have chosen not to because I want to have my full setup scripted so when I setup any new machine I just run my ansible-playbook. This library is nice to just set things up quick and play with them.

nvim-lspinstall

I'm trying to edit a lua file, and got this error which I realize is because I didn't have the Lua language server installed. So using the LspInstall plugin, I did :LspInstall lua which was successful.

Once you have it installed, you can configure it following the configuration of this file: https://github.com/kabouzeid/nvim-lspinstall/wiki. The part that ia bellow the comment "-- lsp-install" works and it was what I used initially when I didn't really know much about configuring neovim.

I am using lspinstall to install language server. It uses this json-language-server. As the docs says jsonc is supported and it allows comments in jsonc filetypes but the lsp is not showing diagnostic if I make any other syntax error. On line 34 i have removed a comma and still lsp showing no diagnostic error in jsonc file.

You could try to use the instructions that nvim-lspinstall uses to install the tailwindcss language server: https://github.com/kabouzeid/nvim-lspinstall/blob/main/lua/lspinstall/servers/tailwindcss.lua (lines 4 - 12)

To manage a VM, you can use something as simple as just manual actions over SSH, or can use tools like Ansible, Hashicorp's Packer and Terraform or other automations. For an app where there is minimal load and security/reliability concern, VMs are still a great option that provide a lot of value for the buck

Server templating: Using Packer has never been easier to create reusable server configurations in a platform-independent and documented manner.

I'll give you hard, but rewarding and easy to modify(once you know what you're doing) way. Packer may be a thing you're looking for.

It is straightforward to build them with packer (I have built AMIs for 13.0 and 13.1, but 13.2 should be exactly the same). I've been meaning to write a blog post about it for a while, but have not gotten to it yet... In any case, what I am doing is using the EBS Surrogate Builder to start an instance running the official FreeBSD 13.2 image with an extra volume attached and run a script to create a zpool on the extra volume and bootstrap and configure FreeBSD 13.2-RELEASE on it. After that packer takes care of creating an AMI out of that extra volume, so you can use it... If you have any issues, let me know, and maybe I will finally get to writing that blog post...

HashiCorp Packer is a tool for creating machine images for a variety of platforms, including AWS, Azure, and VMware. It allows you to define machine images as code and supports a wide range of configuration options.

Packer is a tool that can be used to build machine images. Basically, it takes a base image, runs a series of steps to provision that image, and then burns a new image. In my workplace we use it heavily to build AWS AMIs. But it has an ARM plugin that looks to be very very suitable for building customised Raspberry Pi images (my quick read of the doco there says it can go ahead and write the final image to an SD card for you too).

Seems related to https://github.com/hashicorp/packer/issues/12118 But the workaround discribed in the comments doesn’t seems to work anymore

I'd suggest using a tool like Packer to build a gold image based on your base AMI and all your changes. Then you'll have your own AMI you can launch new instances with.

Your assumption sounds correct. It sounds like you shouldn't focus on migrating specific instances, but instead migrating the template image used for autoscaling into GCP. I tend to prefer Packer for this job, or otherwise recreating the golden image directly on GCP.