Indeed life is ironic…
You can meet a woman who says she loves you, but she still may not choose to be pressing your buttons every day!
Obviously you have not found the right woman.
True, but I’m working on it! 
I don't have a database in every Project @George
agree that if you don't have any databases or git in the project the corresponding options should be off and even hidden as those don't apply
1 Like
if user don't have any databases or git in the project the corresponding options should be off and even hidden as those don't apply
Thank you for understanding. I have nothing but love for these options and they are superb when the Project has both Git and a Database and work faultlessly. I'm about 50/50 on Projects that don't use either. That is the only reason for the suggestion.
I deploy/publish a lot more than I commit to git, I don't have database changes that need to be applied each time, but I always want to clear unused docker images. That means the default toggles all have to be switched nearly every time I publish.
From this:
To this:
I feel having a way to define the defaults for these in the Project Options would be ideal and allow for all Wapplers to set them as they desire.
1 Like
maybe we can just remember the last used options and set those on the next publish action?
2 Likes
Seems like a good alternative to setting in project options. Would the "remember last used" be on a project basis?
It would need to be per project as you wouldn't want to use the same settings from a different project.
I always untick commit to Git, I make commits before I publish
2 Likes
I'd argue this might even be better as per Target (although per Project would be probably cover most)
1 Like
Yep, per target would be good as the targets are per project anyway so that would take everything into account.
Correct, I work from the production database (I keep a local back up though on MAMP PRO server). I don't use the database manager at all other than to refresh schema when I add new tables in Navicat. I have never been able to figure out how to use a development database and a production database.
This is the error that occurs when Publish Database changes is selected. The error makes sense. But it would be nice to be able to have this unchecked by default.
So maybe have it unchecked by default if there is no database running?
1 Like
Please, PLEASE, please remove the check next to database! This keeps catching me out when I forget to uncheck it. Yes my problem but gaaawwwwd dammit argghhhhhhhhhhhhh....
I have a massive bruise on my forehead from keep headbutting my desk when I forget to do it I'm sure I've got concussion now!
2 Likes
This ^^^^^
1 Like