Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion - Add path in config file for pages to generate into. #30

Open
maxresnikoff opened this issue May 12, 2021 · 4 comments
Open
Assignees
Labels
enhancement New feature or request question Further information is requested

Comments

@maxresnikoff
Copy link
Contributor

I quite like to access the CRUD pages by just typing:
domain.com/crud
With the core (generation files) being as such:
domain.com/crud/core

currently, it generates the files to a nested 'app' folder, so to access the CRUD pages, I have to type:
domain.com/crud/core/app

I have moved them out of the app folder, but it is a big hassle whenever we make a database change and have to start from scratch with CRUDDIY again each time.

Would be nice if during the configuration step and file it allows you to enter a path to generate the files into a specified folder.
Eg.

Install Directory:
[ ../crud ]

This way not only will it generate the files into a different directory, but will also allow the changing of the folder from 'app' to something else

@jan-vandenberg jan-vandenberg added the enhancement New feature or request label Mar 30, 2022
@kakohari
Copy link

+1 ❤

@germain-italic
Copy link
Collaborator

@maxresnikoff I'm considering doint this, in regard to #100.

Do you have any other real-world use case I should be aware of?

Also, when you make databases changes, you'll be happy to know that Cruddiy now has a full CRUD configuration backup and restore

@germain-italic germain-italic added the question Further information is requested label Dec 4, 2023
@germain-italic
Copy link
Collaborator

Same question to @kakohari

@germain-italic
Copy link
Collaborator

@maxresnikoff @kakohari the feature is now available in master: #119

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants