We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Add export app to computer button

Home Forums Bug Reports and Feature Requests Add export app to computer button

Tagged: 

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #50622
    PLAN8
    Customer

    Currently you have the option to export application to Verge3D server and export to Verge3D server as a zip file – but no option to export to a local folder option.

    This seems to be quite an obvious function as currently it is unclear what files are unnecessary for the app when hosting on your own server.

    A simple “export app locally” option would be a great help.

    #51026
    PLAN8
    Customer

    Hi,

    Any chance of this being implemented or a comment?

    I’m looking at buying a license, this is probably a clincher for me as it would be my consistent workflow, to self host rather than on a server out of my control.

    Thanks, Andrew

    #51046
    xeon
    Customer

    Hi Plan8

    Just tossing in a two-cent opinion.

    The “applications/projectname” folder contains all the files V3D needs. Prior to publishing it’s the publisher’s responsibility to modify that folder as needed to fit their specific hosting needs.

    At the simplest this will include removing:
    the files associated with your 3D program blender, maya, or max.

    Then if you are using compression, remove the unneeded non-compressed files such as .gltf and .bin.

    You will also need to determine if you are using the standard verge, icons or if you are creating your own and replacing those if needed.

    You will also want to go through and delete your backup files.

    And finally, you will want to validate any textures and ensure that only textures your app is using are stored in the folders.

    Once you are done with all that you have a clean folder that can be used for uploading.

    Your workflow is probably unique but for many, it is something like this:
    1. Create the project
    2. Develop the project
    3. Test local
    4. Rework as needed
    5. Test local
    6. if good push to soft8soft or local server
    7. Test
    8. Rework as needed
    9. Test locally
    10. Copy project in App Manager to final_project name
    11. Test New copy (final_project)
    12. go to the application folder and delete unnecessary files and update files as needed within the final_project
    13. Test New copy locally
    14. Uploaded to a Staging server
    15. Test
    16. Upload to Production server

    This process provides you a copy of your project with all its backups and working files as well as a version that is cleaned up, optimized and stripped of all backups and working files. This will be important if there are requested changes that require you to back track.

    Regardless, if you choose to use this process or not, the applications/project name folder is the folder that contains all the files you need. You choose how clean you want it to be. But the files are there….no need to export.

    Xeon
    Route 66 Digital
    Interactive Solutions - https://www.r66d.com
    Tutorials - https://www.xeons3dlab.com

    #51048
    PLAN8
    Customer

    Hi Plan8

    Just tossing in a two-cent opinion.

    The “applications/projectname” folder contains all the files V3D needs. Prior to publishing it’s the publisher’s responsibility to modify that folder as needed to fit their specific hosting needs.

    At the simplest this will include removing:
    the files associated with your 3D program blender, maya, or max.

    Then if you are using compression, remove the unneeded non-compressed files such as .gltf and .bin.

    You will also need to determine if you are using the standard verge, icons or if you are creating your own and replacing those if needed.

    You will also want to go through and delete your backup files.

    And finally, you will want to validate any textures and ensure that only textures your app is using are stored in the folders.

    Once you are done with all that you have a clean folder that can be used for uploading.

    Your workflow is probably unique but for many, it is something like this:
    1. Create the project
    2. Develop the project
    3. Test local
    4. Rework as needed
    5. Test local
    6. if good push to soft8soft or local server
    7. Test
    8. Rework as needed
    9. Test locally
    10. Copy project in App Manager to final_project name
    11. Test New copy (final_project)
    12. go to the application folder and delete unnecessary files and update files as needed within the final_project
    13. Test New copy locally
    14. Uploaded to a Staging server
    15. Test
    16. Upload to Production server

    This process provides you a copy of your project with all its backups and working files as well as a version that is cleaned up, optimized and stripped of all backups and working files. This will be important if there are requested changes that require you to back track.

    Regardless, if you choose to use this process or not, the applications/project name folder is the folder that contains all the files you need. You choose how clean you want it to be. But the files are there….no need to export.

    Hi there, that’s really helpful (particularly the bit about which files are unnecessary).

    This is kind of my point though – this is a lot of work to just export the bare minimum file required to self host. I don’t think it would be all that difficulty to have a single “Export to local” option that just does exactly that – just export the minimum required files to serve on a self hosted website.

    I am testing using the Verge3D wordpress plugin, this asks for a folder to upload and if you point it to the project folder, it uploads EVERYTHING – this is an immense waste of time, bandwidth and storage and often fails as the blender files can be very large.

    Deleting unrequired folders out of the working folder is destructive, so a copy folder must be made manually and the unnecessary files deleted manually as well, again, all very time consuming and quite confusing when a simple export button would make the whole process streamlined, pleasant and simple.

    So – a simple export to local option seems quite a logical option to me? I would have thought seeing as there is a dedicated wordpress plugin, then it makes sense that a streamlined export for that exact purpose would make sense?

    #51077
    PLAN8
    Customer

    Or, how about automatically when creating a new app folder, all the background creation files (blender and backup files etc) are automatically listed in one folder and all the required HTML app files in another –

    #68900
    PLAN8
    Customer

    Dragging this up again as it seems a must to me –

    A button to export only the required HTML/web based set of files only that doesn’t include files that are not required for the web version (ie all the Verge3D and blender files as well as unused textures etc).

    Or, make the Verge3D folder hierarchy keep the exportable HTML files separated from the design and backend files in the first place so that manual export or copy of the web ready files is a simple case of copy and paste.

    It really does seem like this should be a standard part of the workflow to me, given that the whole point of Verge3D is to enable Blender to Web processing.

    • This reply was modified 11 months, 4 weeks ago by PLAN8.
    #68906
    PLAN8
    Customer

    Yep – this is the simplest and quickest solution IMHO

    I can imagine, that wouldn’t be too hard to implement either

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.