this is a "bugmenot" account I found, I use sometimes when forgot my ufd with me.
That's ok, I like Stef thought I'd recommend getting one of these in the future:
or whatever you like, a temporary ftp account may also fit better....
Only 1 day is enough to leave something useful which would hopefully not give reason to PSC you and others write lies and stupid logic anymore.
Yes, I agree that logic is mostly a waste of time but sometimes it can be useful.
For example, creating an FTP account even if temporary will:
a ) require installing an FTP service on the server
b ) require my time configuring the service
c ) require being removed after you upload everything
Logically, I assume that even thought you say "1 day", I'm sure that you will inevitably need to change something again in the near future and then I'll have to go through steps a, b, c again which is time consuming.
I can also assume as logical facts that:
- There is not enough enough room on dropbox to hold LiveXP size
- We had troubles in the past when trying to use dropbox to share files
- We can't use multiple dropbox accounts on the server.
So, using the results from considering a factual logic we can now resort to popular proverbs as a never-ending source of wisdom and inspiration.
For example, there is a saying in my country (perhaps yours as well) that goes like:"If you have a difficult and time consuming task to perform, give it to a lazy guy that he will surely find the easiest and quickest way of getting it done."
On this case, I'm the lazy guy and you're giving me the task of updating your project server.
So, I would propose the following solution:
- Ask galapo to create a new user on his server with limited SSH permissions;
- This user can only read files on the LiveXP server;
- Give the login details of this user to Nuno;
- Nuno sets up a cron
job using scp
to copy files from remote server onto boot land server at each 24 hours
You and Galapo can now update the server on your own machine and the results appear at boot land after some hours without giving me
any additional work.
Mission accomplished team!
Then, please, for goodness sake don't call some winbuilder.exe oddity a "release candidate" if in fact you don't really mean it.
Actually, Peter is the person responsible for all the pre-versions and I'm the person who only signs out the new stable versions when I'm happy with the result. I don't call them RC, I commonly call them all as "unstable
" and "I'm not fit for your production environment
" type of releases but that's just my opinion.
One of the concerns that I've heard from Peter is that betas got ignored and he only hears feedback when a new binary "looks" serious like a RC.
He has been working for free all these years. Getting feedback from users is a little pay back that keeps him happy and motivated to keep on moving. Either right or wrong, pushing away the only guy that was still solving bug reports doesn't get us very far, does it?
I'm still confused about this development model and what you actually mean
This model is a new type of rocket science: http://www.boot-land...showtopic=10500
Peter was confused, Galapo was confused after reading that link so I guess it was better to keep on with the WinBuilder 075 beta 19abc
type of releases that are surely more understandable to everyone else.
fundamental syntax of the winbuilder engine being repeatedly altered, script developers not being included in the decision making
This is fundamental yada, yada
. It's been 8 months since 080 release and at the current level of motivation there won't exist syntax changes ever
again, are we
all happy now?
script developers were too
involved in decision making and now we all pay the price for this decision that keeps us away from any attempts of improvement either in winbuilder.exe or new wb projects.
You guys lead the future, don't let us down.