nsinnovations/ns_erpnext_app
2
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

Investigate building with bench #5

New Issue
Closed
opened 2026-04-14 12:12:38 +00:00 by TyReynolds · 4 comments
TyReynolds commented 2026-04-14 12:12:38 +00:00
Member
Copy Link

I looked into it and I believe I know how to go about it. I want to add a feature flag to the site config that acts as a toggle for my "save to auto pay" check box. This will shut off the feature until I have it done and ready for production keeping it save to push with no worries of the untested feature making any headaches. Only problem is that I can't seem to open the site config at the moment and I'm not sure why. I've edited it many times before, but it says it doesn't exist now even though I can see it in the directory. My other option is, test and finish the feature then I can push all to production and I don't need the feature flag.

I looked into it and I believe I know how to go about it. I want to add a feature flag to the site config that acts as a toggle for my "save to auto pay" check box. This will shut off the feature until I have it done and ready for production keeping it save to push with no worries of the untested feature making any headaches. Only problem is that I can't seem to open the site config at the moment and I'm not sure why. I've edited it many times before, but it says it doesn't exist now even though I can see it in the directory. My other option is, test and finish the feature then I can push all to production and I don't need the feature flag.
TyReynolds commented 2026-04-14 12:16:55 +00:00
Author
Member
Copy Link

Other than that, the deployment should be easy. From the bench root, "bench restart" will apply the api changes (Python), "bench build" will push the front-end changes (JS), and if we feel the DB needs updated, which it shouldn't, we can run "bench --site "site name" migrate". This should be all then after a cache refresh it should all be there.

Other than that, the deployment should be easy. From the bench root, "bench restart" will apply the api changes (Python), "bench build" will push the front-end changes (JS), and if we feel the DB needs updated, which it shouldn't, we can run "bench --site "site name" migrate". This should be all then after a cache refresh it should all be there.
TyReynolds commented 2026-04-14 12:29:23 +00:00
Author
Member
Copy Link

I looked into it and I believe I know how to go about it. I want to add a feature flag to the site config that acts as a toggle for my "save to auto pay" check box. This will shut off the feature until I have it done and ready for production keeping it save to push with no worries of the untested feature making any headaches. Only problem is that I can't seem to open the site config at the moment and I'm not sure why. I've edited it many times before, but it says it doesn't exist now even though I can see it in the directory. My other option is, test and finish the feature then I can push all to production and I don't need the feature flag.

** UPDATE **

Some reason I code just write to it with nano command, so I got the flag in.

> I looked into it and I believe I know how to go about it. I want to add a feature flag to the site config that acts as a toggle for my "save to auto pay" check box. This will shut off the feature until I have it done and ready for production keeping it save to push with no worries of the untested feature making any headaches. Only problem is that I can't seem to open the site config at the moment and I'm not sure why. I've edited it many times before, but it says it doesn't exist now even though I can see it in the directory. My other option is, test and finish the feature then I can push all to production and I don't need the feature flag. ** UPDATE ** Some reason I code just write to it with nano command, so I got the flag in.
TyReynolds commented 2026-04-16 12:45:11 +00:00
Author
Member
Copy Link

We must pull from git on the production server and run just the build and restart commands from the bench route. We do need to update the prod servers site config before the deployment.

We must pull from git on the production server and run just the build and restart commands from the bench route. We do need to update the prod servers site config before the deployment.
TyReynolds commented 2026-04-27 19:00:43 +00:00
Author
Member
Copy Link

Found the proper commands and order to run them in. All are in the new README I recently pushed.

Found the proper commands and order to run them in. All are in the new README I recently pushed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
TyReynolds norman
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nsinnovations/ns_erpnext_app#5
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?