Hi, is there some skeleton or something if you are...
# compose-desktop
v
Hi, is there some skeleton or something if you are on to a plain new project? Im having trouble with keeping up to date. I'm interested only in desktop, dont need mobile/web versions.
r
v
tnx
m
If you're using Conveyor for distribution (or thinking of using it) you can also run
conveyor generate compose com.example.my-app
, it'll generate a CfD app with packaging and other things built in. See: https://conveyor.hydraulic.dev/15.0/tutorial/hare/jvm/
s
@mikehearn Hello Mike - I am already distributing my Desktop app using Conveyor, I am now looking at the new releases 15.1 and want to test the Update control API. What would be the best flow so i can test without having to publish a new version on the release site URL / repository. Should i have separate values for
site.base-url
&
vcs-url
in the conf file for testing purposes? like a staging vs release env I would like to fully the test the Update control flow before release an app update with the control flow code to my users
m
Yes you can do that. Just create a
staging.conveyor.conf
file that has
include "conveyor.conf"
at the top, then override any values you want. You can test against a localhost server, or if you want a truly separate update site and if your product is commercial, use one of the other license keys you got when you purchased (there should have been three).
s
Ok thanks Mike - I use the commercial version so will test setting up a separate update site.