# |
Sep 22nd 2011, 07:07 |
rchavik |
in 1 git commit |
# |
Sep 22nd 2011, 07:07 |
diverdude |
in a changeset? |
# |
Sep 22nd 2011, 07:07 |
rchavik |
otherwise you'll have a big commit adding 100s of files |
# |
Sep 22nd 2011, 07:07 |
rchavik |
in a changeset.. |
# |
Sep 22nd 2011, 07:06 |
rchavik |
diverdude, i've if have 100s, i will still do it one by one, the commit to git for each baked files |
# |
Sep 22nd 2011, 07:06 |
Section58 |
will be deleted before your app goes live |
# |
Sep 22nd 2011, 07:06 |
lorfds |
does anyone have any experience with this? what is the best solution> |
# |
Sep 22nd 2011, 07:06 |
Section58 |
about 60%-80% of the code produced from bake |
# |
Sep 22nd 2011, 07:06 |
lorfds |
I would like to push code from github to a shared host....specifically bluehost |
# |
Sep 22nd 2011, 07:06 |
diverdude |
rchavik, but how many tables do you have? |
# |
Sep 22nd 2011, 07:06 |
rchavik |
i alway bake one model, then its controller, then its views |
# |
Sep 22nd 2011, 07:06 |
Section58 |
also, don't be scared to delete the crap code it projuces |
# |
Sep 22nd 2011, 07:06 |
rchavik |
diverdude, i use bake all the time, but i never use 'all' |
# |
Sep 22nd 2011, 07:05 |
Section58 |
so lets say you have a multitree behavoir, with a higharcial structure with a table called root_id .... that will break it |
# |
Sep 22nd 2011, 07:05 |
diverdude |
true...just is hacky...if i need to re-cake i have to do it over again |
# |
Sep 22nd 2011, 07:05 |
Section58 |
*bake will |
# |
Sep 22nd 2011, 07:05 |
Section58 |
bake with mash it as it sees it |
# |
Sep 22nd 2011, 07:05 |
Section58 |
bake doesn't make the whole thing, and if your naming conventions are slightly wrong |
# |
Sep 22nd 2011, 07:04 |
Section58 |
then add on the specials a the end |
# |
Sep 22nd 2011, 07:04 |
Section58 |
you could build all of it |
# |
Sep 22nd 2011, 07:04 |
Section58 |
if you deleted the table that errored |
# |
Sep 22nd 2011, 07:04 |
Section58 |
but logically |
# |
Sep 22nd 2011, 07:04 |
Section58 |
remmber that i don't use bake |
# |
Sep 22nd 2011, 07:04 |
diverdude |
Section58, but how can i then avoid it to be process by all? |
# |
Sep 22nd 2011, 07:03 |
Section58 |
it will not |
# |
Sep 22nd 2011, 07:03 |
Section58 |
no |
# |
Sep 22nd 2011, 07:03 |
diverdude |
Section58, so if i generate cake_sessions manually first it will be skipped when i do all afterwards? |
# |
Sep 22nd 2011, 07:02 |
Section58 |
as they are not special like cake_sessions |
# |
Sep 22nd 2011, 07:02 |
Section58 |
may or maynot handle the 'all' pram |
# |
Sep 22nd 2011, 07:02 |
Section58 |
the other tables |
# |
Sep 22nd 2011, 07:02 |
Section58 |
and you can make the x at that point |
# |
Sep 22nd 2011, 07:02 |
diverdude |
thats a huge task for 63 tables |
# |
Sep 22nd 2011, 07:02 |
Section58 |
pick the cake_session model (it should list it) |
# |
Sep 22nd 2011, 07:02 |
diverdude |
Section58, that means one by one |
# |
Sep 22nd 2011, 07:02 |
Section58 |
and use the options |
# |
Sep 22nd 2011, 07:02 |
Section58 |
start with 'cake bake' |
# |
Sep 22nd 2011, 07:02 |
dakota |
diverdude: remove the cake_sessions table temporarily then |
# |
Sep 22nd 2011, 07:01 |
diverdude |
Section58, what kind of bits? |
# |
Sep 22nd 2011, 07:01 |
Section58 |
do it in bits |
# |
Sep 22nd 2011, 07:01 |
diverdude |
i need to do this automatically |
# |
Sep 22nd 2011, 07:01 |
Section58 |
diverdude: don't do it 'all' |