adevx

In my case yes and yes, but mostly because I spread out over two cloud providers.

Fantastic news. I deploy WireGuard to provide a private network (mesh) between VPS servers. Each VPS instance has each other vps as peer. So no single source of failure. I run PostgreSQL with Patroni and GlusterFS over this mesh with no issues. When I add or destroy a VPS with Ansible all VPS nodes get an updated config and reload. This way I don't rely on a single cloud provider because I do not use their private network service.

This seems to be default practice now. I also found this to be the case for Outlook accounts. After initial registration they block your account, or in the case of Outlook, disable outgoing email.

Thanks, I guess it's a bit early for me to jump to conclusions. I'll just have to wait and see what you guys come up with :-)

This is painful. I am finalizing a 4 month migration to Typescript using the now abandoned Vue class based decorator approach (including Vuex Decorators) Even though the migration probably is a 50% split between frontend and backend, it looks like a lot of time has been wasted.

I always edited this file than used

  chattr +i /etc/resolv.conf 

to prevent further modifications.

Thanks for the link. Good to see this is much easier now.

As you probably know, Nuxt.js uses a folder to url mapping, so say /src/views/contact/index.vue maps to /contact In my case I wanted to be able to change the url depending on the language of the user. And not by prefixing it with a /en/contact vs /de/kontact. To make matters more complicated, I serve multiple domains from the same node/express instance and determine the correct site data to render based on the domainname. There were plugins and hacks to make this somewhat possible, but it felt like going against the philosophy of nuxt.js. I still think it's a fantastic framework if your needs align with this type of routing. I ended up using the Vue SSR HackerNews repo as a template.

This. I started out with a similar framework called nuxt.js but found the routing to be too limiting. It's a nice way to get started quickly, but once things become more complex you hit too many hurdles. In the end it pays to do the project setup yourself, which also helps a ton in debugging issues along the way.

There is also bootstrap-vue.js.org/ which does not use jQuery.

I agree that I did not replicate the theme and plugin system of WordPress. But the beauty is that you probably don't have to. WordPress has to cater to all, which is probably the source of all the issues people face.

But neither is my website a simple brochure site. Members create their own content, upload photos, enter their location on a map, enter available dates, have the ability to chat with other members. When I tried to do al this with custom and available plugins, it never felt as a coherent experience. Then there is a lot of automation in the background, notifying members of unanswered messages, expiring profiles, notifying members of expiring memberships. Getting all this properly done with the CMS provided API's is more work then writing it from scratch yourself. With the benefit of not having to worry about CMS API deprecation.

For what it's worth, I went with PostgreSQL, decided not to use an ORM but a query builder (knex.js). Knex.js gives you database migrations and is good for basic querying. It is easy to drop down to raw SQL if you need something more complex or optimized.

I know this is not for everyone, but sometimes it makes sense to jump off the CMS bandwagon and build a custom site. First I used Drupal but got tired of rewriting the site on every major release and jumped on WordPress. Then on WordPress I realized I could not create the user experience I was after without committing massive amounts of time and resources in custom plugins/themes. Leaving me too dependent on a moving target that might take a direction I don't agree with. It looks like there is a plugin for everything, but having them all play nice together is difficult. The more plugins the bigger the security risk, and the greater the risk of an update breaking your site.

I rewrote the site in Node.js/Express with Vue.js and server side rendering. The ecosystem is ready with so many libraries to quickly get up and running. Another major benefit is being able to design your own database instead of having everything stored as a post (WordPress).

Paying off big-time now :-)

To be honest, I was already considering the switch. Mainly because I have production servers on Ubuntu and having the same dev environment as the server makes sense. Regardless, if possible I still like to align myself with companies I feel passionate about, IBM is no such company.

I am at this very moment switching from Fedora 29 ( I was on the early Beta) to Ubuntu because of the acquisition by IBM. It just doesn't sit right with me. Just made the last backup before plugging in the USB with Ubuntu 18.10.