I had my website deployed as a virtual host using web station. Then I moved it into a virtual DSM where I setup web station and backends etc. Exactly the same (restored a hyper backup of web station and website files/databases into the VM then uninstalled same from the main NAS). Then to get to it over the web, my NAS has a reverse proxy that routes the traffic to the VM. The way it's setup the only port that will... Source: almost 2 years ago

I am trying to spin up a saas product where I would ideally sell the "checkout page" ( think of the product as a mini-Shopify ). Right now the front-end is done in react where I think the elements of that page is probably going to be some NPM package ( most like https://stripe.com/payments/elements ). And the back-end API is built in NestJS ( Swagger ) connected to an AWS database. Source: about 1 year ago

I see now. Do you see this image [0] on https://height.app/compare/asana? Now that's what I wanted to see, now I understand it's some sort of task manager for teams that presumably integrates with GitLab, GitHub etc. --- Ok on a further look, I think I understand what happened. You linked directly to https://height.app/product/automations, but I and probably others who see this post would have thought that it was... - Source: Hacker News / over 1 year ago

Stripe Elements is the option we’ll discuss today. Elements are pre-built form components that you can embed directly into your web application (there’s mobile versions too!). There’s an official react-stripe-js library that exposes the new PaymentElement. The PaymentElement supports several payment methods and is the best default. You should only implement individual elements (like one for Card and one for SEPA)... - Source: dev.to / about 2 years ago