Thread: [Cppcms-users] Specify folder for temporary upload files
Brought to you by:
artyom-beilis
From: Julian P. <ju...@wh...> - 2010-07-29 01:00:32
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hallo, is there a way to tell cppcms where to store the temporary files it creates on multipart/form-data uploads? I need this because the application I'm currently writing shall run on an embedded device which loads from a read only filesystem and has only a certain path where data can be stored persistently. (/tmp is a RAM disk, but the problem is, that the available RAM is not big enough to hold the upload until it is save'd_to somewhere -> embedded device). Thanks for your solutions, Julian -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJMUMjWAAoJENidYKvYQHlQx2AQAMwg28sMMaGc3AJp2DsuCJ1W j71qe7tbb/1H9x32VKYzAtso/RzphzztlyprsphA/KbpHpCPDFlNgM+5CM1li0kh CQxn1mc4/y0WhMzGPa7cH5wKpMhP4DG2R0jvc4e2aqIZie6TJMJxXbgZWXH/2ll4 dukmsjFuDvRlMjmFA6QErQmee350G/IhFC63aAzQH0X5KC43UVMqbuRIv2comWs8 hApcku5Eo/lNyEB7Dt24L7TuBIY2Y9/jaGHZXPmyBT8ZCU/R0ZQAW+g2q1XTt2av /k+cmraDclUHl363gFCinV1KfUSNuYMIfDyygQ986Q+jXfOccwtxI2Rtz1UkdhKN SPrdZgOcTCfwBzHxefkiihfie86YxgeJ3PVMyXXF6Rvky2oM+ocj6KxS6jhYM90o VtSELX1uReaeKgfPwujDal0aOfu8ZJqUekwInGyfxkVJpKB4sXSgNOi9FWBA8X5l qAFB6oKemOgHNTnBoZYZzPW6XpbqmYnkiVpfGtsLzHWbVnnwRTbzAFXz486F1s4M c2VoG/7dxXREx8RoP4M113wWMXFWgD8ovv07i8ar6QO5ZMCLB8JqIrkt03ymQOGw dQv1ztkcDICFEA+GU46UwD3uD9TFfzw+ke2ONMtGUpuUmNma80jCSQLm0s2UFCgt 7yev6LbCoD2XPzGIWmwp =kjrJ -----END PGP SIGNATURE----- |
From: Artyom <art...@ya...> - 2010-07-29 12:49:01
|
Hell, Take a look on this: <http://art-blog.no-ip.info/wikipp/en/page/cppcms_1x_config#security.uploads\_path> But you need to take the latest version from SVN - revision 1327 or above. I have just added these options I've planned to add long time before but hadn't get there. Artyom > > is there a way to tell cppcms where to store the temporary files it > creates on multipart/form-data uploads? > I need this because the application I'm currently writing shall run on > an embedded device which loads from a read only filesystem and has only > a certain path where data can be stored persistently. (/tmp is a RAM > disk, but the problem is, that the available RAM is not big enough to > hold the upload until it is save'd_to somewhere -> embedded device). > |
From: Julian P. <ju...@wh...> - 2010-07-29 15:44:23
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 29.07.2010 14:48, schrieb Artyom: > Hell, > > Take a look on this: > > <http://art-blog.no-ip.info/wikipp/en/page/cppcms_1x_config#security.uploads\_path> > > > > But you need to take the latest version from SVN - revision 1327 or above. > I have just added these options I've planned to add long time before but hadn't > get there. > > Artyom > > > Thanks, this answered my question, but just raised another: in the named documentation it reads that the path for temporary files is otherwise made from the TMP or TEMP environment variable. This variable is not set in my environment (Linux), so where from does the upload method take the path to store to instead? Would it be enough to run my application with TMP="/path/to/writable/dir" myapp.fcgi if I didn't want to use an unstable SVN revision? How unstable is the SVN revision indeed? Does it make a big difference to use the latest SVN version compared to the current beta? Thanks for your reply, Julian -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJMUaHGAAoJENidYKvYQHlQhckQALY+a/NZtHQDsu8QPbGsXmef zgi0tKoImd/FkSDTV6fkaYhEgEjYP+DTEM/buQICXI8xZt9Oh+8Pq4o2c4qOulR7 m4sVE9nMWj91R7V5A2UA9CAgAyplAKmzfN7t3duSKtfyxuQQGI0zc5afCazjwT0x eTcpdK6ConInvhoWWi6AOiDn/j8dqi2S73rpKETam79+ANHnkfJ6ATdRApTTinoz 1dulCZ0dXSnUYEAfFBPNSCh/K1A+4QHXb3NxmJ/oXToWI2MpI4z1NlkvG0kAVgWH emsD24HhdXhIz3wemt0sF6GxbK/NNyQVEXpLr7wCwUbBwH1CvVoX6zjXxKLPlkY+ XxILBfEVWp+sEOx2XhX9pSIHQ5CdrqF4rNqSR476w9a7sWMZZx1Z3prO/CFwprij 1728uh4ry8SI77ot3Mw2uetmg4v4yxcX5MoC5lFRzqEq4dnkAMO1zf5RmlgiSaqD kVhHRibZiH/PQpK5Bmcv+yqJipsSAbmdFVEQE2oobbaZ/uVeIzrhY0dqQ4j4vuGJ jYP0DYMbL89tXVAhS6MD8rxM4Nmdoc3PaVwuAY7Fk0sHqhckdeOlBwLq9uHpl66F vhROQtlI2dIrzTiP17fg5387IcoALppPlad1FBNvZB+4NwFaqoRef8OOf5KAbLFI c1Sts4GB39gMGm72v7Q4 =M/K0 -----END PGP SIGNATURE----- |
From: Artyom <art...@ya...> - 2010-07-29 16:10:47
|
> > Thanks, this answered my question, but just raised another: in the named > documentation it reads that the path for temporary files is otherwise > made from the TMP or TEMP environment variable. This variable is not set > in my environment (Linux), so where from does the upload method take the > path to store to instead? In /tmp so this is not a problem, fixed docs. > Would it be enough to run my application with > TMP="/path/to/writable/dir" myapp.fcgi Yes, this should work >i f I didn't want to use an > unstable SVN revision? How unstable is the SVN revision indeed? Does it > make a big difference to use the latest SVN version compared to the > current beta? There are no big differences, but I would do recommend you to take an svn version as it includes some fixes with file u[;pad handling that was founded when I added several test cases for these configuration options. So if you upload files, it is better to take svn version. About stability, generally it is as stable as beta, but time to time there may be small issues. So just don't update to every latest revision and listen to what happens on this mailing list. Artyom |