You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently adding any custom JS/CSS means, the person has to manually fork and edit the code, would request for an environment variable which can take the source of a JS/CSS file to be included at <head>
Proposal can be: PASTY_CUSTOM_CSS and PASTY_CUSTOM_JS which would hold values to URLs having the JS/CSS respectively.
The text was updated successfully, but these errors were encountered:
Thank you for your idea!
I personally think that this feature would bloat pasty a bit too much, but I'll suggest an alternative:
You actually don't have to fork and re-compile the whole project to inject custom CSS/JS or perform any other modifications to the frontend as it is a simple folder inside the Docker container.
You can just manually mount this exact folder using Docker volumes and perform any modifications directly in the frontend code itself without having to re-compile or re-deploy the service.
If you need any further advice feel free to ask in this issue ^^
Currently adding any custom JS/CSS means, the person has to manually fork and edit the code, would request for an environment variable which can take the source of a JS/CSS file to be included at
<head>
Proposal can be:
PASTY_CUSTOM_CSS
andPASTY_CUSTOM_JS
which would hold values to URLs having the JS/CSS respectively.The text was updated successfully, but these errors were encountered: