ChatPad on Cloudron - ChatGPT Artificial Intelligence Interface
-
Done, the package is ready and running fine on my Cloudron Instance.
The package can be found in GitlabAs this is my second package, and I didn't get yet Feedback for my first package, I am asking for feedback, if I did that packaging the right way

-
Done, the package is ready and running fine on my Cloudron Instance.
The package can be found in GitlabAs this is my second package, and I didn't get yet Feedback for my first package, I am asking for feedback, if I did that packaging the right way

@Kubernetes said in ChatPad on Cloudron - ChatGPT Artificial Intelligence Interface:
I am asking for feedback
overall format looks good, but for an 'adopted' Cloudron app, Dockerfile
FROMshould be the Cloudron base image
FROM cloudron/base:4.0.0@sha256:31b195ed0662bdb06a6e8a5ddbedb6f191ce92e8bee04c03fb02dd4e9d0286dfand then do something to pull in the code from the source repo (but there are other ways)
ADD https://github.com/CorentinTh/it-tools/archive/refs/heads/main.tar.gz /app/code RUN tar -xzf main.tar.gz && rm main.tar.gz && mv it-tools-main/* . && rm -r it-tools-mainBut maybe others with more experience and authority can advise otherwise.
For a custom app which is only to be used by author or small group, if it works, it works.
For a custom app which might be adopted with refinements into the App Store, I think it is better to take the above approach. -
Done, the package is ready and running fine on my Cloudron Instance.
The package can be found in GitlabAs this is my second package, and I didn't get yet Feedback for my first package, I am asking for feedback, if I did that packaging the right way

@Kubernetes said in ChatPad on Cloudron - ChatGPT Artificial Intelligence Interface:
Done, the package is ready and running fine on my Cloudron Instance.
The package can be found in GithubAs this is my second package, and I didn't get yet Feedback for my first package, I am asking for feedback, if I did that packaging the right way

Thank you for doing that.
-
@Kubernetes said in ChatPad on Cloudron - ChatGPT Artificial Intelligence Interface:
I am asking for feedback
overall format looks good, but for an 'adopted' Cloudron app, Dockerfile
FROMshould be the Cloudron base image
FROM cloudron/base:4.0.0@sha256:31b195ed0662bdb06a6e8a5ddbedb6f191ce92e8bee04c03fb02dd4e9d0286dfand then do something to pull in the code from the source repo (but there are other ways)
ADD https://github.com/CorentinTh/it-tools/archive/refs/heads/main.tar.gz /app/code RUN tar -xzf main.tar.gz && rm main.tar.gz && mv it-tools-main/* . && rm -r it-tools-mainBut maybe others with more experience and authority can advise otherwise.
For a custom app which is only to be used by author or small group, if it works, it works.
For a custom app which might be adopted with refinements into the App Store, I think it is better to take the above approach.@timconsidine Thanks for the feedback. I didn't notice that I should use the cloudron base image. I will try to it in the work I already have done and update then.
-
Okay, I have done it. The package is ready from my point of view and could be published in Cloudron App Store.
Thanks to all for the feedback and support.
-
Will take a look later. Thinking/hoping it will be better than my self-package of the other one (chatbot-ui).
I don't suppose you feel up to the challenge of packaging Flowise ?
https://forum.cloudron.io/topic/9130/flowise-ui-for-langchain?_=1685224667920Working with regular ChatGPT, even V4, the knowledge cut-off date is sometimes problematic or time-wasting.
Being able to include more current resources (like developer updated docs) is likely to be super helpful.
or so I hope -
Will take a look later. Thinking/hoping it will be better than my self-package of the other one (chatbot-ui).
I don't suppose you feel up to the challenge of packaging Flowise ?
https://forum.cloudron.io/topic/9130/flowise-ui-for-langchain?_=1685224667920Working with regular ChatGPT, even V4, the knowledge cut-off date is sometimes problematic or time-wasting.
Being able to include more current resources (like developer updated docs) is likely to be super helpful.
or so I hope@timconsidine Interesting tool, I tried, but first attempts did fail because of the read-only filesystem in Cloudron...
-
@timconsidine Interesting tool, I tried, but first attempts did fail because of the read-only filesystem in Cloudron...
@Kubernetes I am trying also but running into errors
Will try again later -
@timconsidine Interesting tool, I tried, but first attempts did fail because of the read-only filesystem in Cloudron...
@Kubernetes said in ChatPad on Cloudron - ChatGPT Artificial Intelligence Interface:
because of the read-only filesystem in Cloudron
Shhhh, don't tell @girish or @nebulon but sometimes I try to "bypass" this issue to get a proof of concept by installing to
/app/data
Just to see it if builds and works.
Then think about separation of code and data -
Okay, I have done it. The package is ready from my point of view and could be published in Cloudron App Store.
Thanks to all for the feedback and support.
@Kubernetes said in ChatPad on Cloudron - ChatGPT Artificial Intelligence Interface:
Okay, I have done it. The package is ready from my point of view and could be published in Cloudron App Store.
Well done

I have a built the package, it installed smoothly and runs nicely.
Thank you for your work on this. I may stop using the desktop version.The Docker image is large : 5Gb. Surprised me (but heck, what do I know).
I wonder if there is a way to reduce the size of the image during the build process.
But I am no expert in Docker, so not sure.
I didn't see anything obvious in the Docker file.
Maybe a multi-stage build ? But I don't much about that. -
I moved the repo to the Cloudron Gitlab
Regarding size, 5Gb is really big. But maybe someone with experience in shrinking the Docker images can give some advise.
-
I have updated the Dockerfile to remove unrequired software and use of multi stage for build and production.
-
I have updated the Dockerfile to remove unrequired software and use of multi stage for build and production.
@Kubernetes oooo ! Will take a look
-
L LoudLemur referenced this topic on
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login