Creating an on-prem product?
I'm looking to create a webapp that end users can deploy within their environments. this goal would seem to be a bit of an antipattern given the wealth of integrations ootb. Is anyone else working with wasp in this way?
9 Replies
Hi @tk-421. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources provided, there isn't specific information about creating on-premises products with Wasp or using Wasp for applications that end users can deploy within their own environments. However, I can provide some relevant insights about Wasp's deployment capabilities and flexibility:
1. Wasp is designed to build full-stack web applications, and it generates deployable code that can be deployed in various ways. As mentioned in the Deployment Overview, Wasp apps consist of a Node.js server, a static client, and a PostgreSQL database, which can be deployed "anywhere" where you can usually deploy Node.js apps or static apps.
2. While Wasp offers a single-command deployment through its CLI, it also supports manual deployment. This means you have the flexibility to build your Wasp app and then deploy it manually to various environments, as described in the Deploying Manually documentation.
3. There's an open GitHub issue discussing deployment to bare metal, which mentions the possibility of using Docker containers and docker-compose for deployment. This approach could potentially be adapted for on-premises deployments.
4. Regarding vendor lock-in concerns, a community member asked a similar question, and the response suggests that Wasp generates standard code that can be used independently. From the Discord conversation, it appears that you can take the generated code and move away from Wasp if needed.
While these points suggest that Wasp has some flexibility in deployment options, the knowledge sources don't provide specific information about creating on-premises products or end-user deployable applications with Wasp. If this is a critical requirement for your project, you may want to reach out to the Wasp community or developers directly to discuss the feasibility of such an approach.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @tk-421, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@tk-421 I'm working on a dead simple gitops / k8s setup with Wasp, I'll open source a template for it tomorrow
Wohooo @space black, you just became a Waspeteer level 3!
Oh sweet man thanks. Look forward to seeing it.
cc: @Filip
Hey @tk-421, can you give me some more details? What are you building, why would it be an antipattern, etc? Maybe I can point you in the right direction
Just to chime in - we had people deploy apps on perm and we added recently self-hosting info to our docs
Hey @Filip the thought is to build a security tool that has a web app front end but would run in the end users environment. So all of those multitenant capabilities of wasp would seem unnecessary. I wouldn't want to make it difficult for rhe end user to self host.
I don't think that should be a problem. You could just use the stuff you need, and Wasp won't generate the stuff you don't use 🙂