mirror of
				https://github.com/gristlabs/grist-core.git
				synced 2025-06-13 20:53:59 +00:00 
			
		
		
		
	(core) Fix flyctl memory settings, since requested memory flag wasn't being used
Summary: After removal of 'scale' command in https://phab.getgrist.com/D3983, memory settings stopped applying properly to the actual machines that fly starts. This change restores them. Test Plan: Tested by examining the memory allocated to a fly machine with and without this change. Reviewers: georgegevoian Reviewed By: georgegevoian Differential Revision: https://phab.getgrist.com/D4063
This commit is contained in:
		
							parent
							
								
									9d10ac8292
								
							
						
					
					
						commit
						996674211d
					
				@ -67,7 +67,8 @@ const appExists = (name) => runFetch(`flyctl status -a ${name}`).then(() => true
 | 
			
		||||
const appCreate = (name) => runAction(`flyctl launch --auto-confirm --name ${name} -r ewr -o ${org} --vm-memory 1024`);
 | 
			
		||||
const volCreate = (name, vol) => runAction(`flyctl volumes create ${vol} -s 1 -r ewr -y -a ${name}`);
 | 
			
		||||
const volList = (name) => runFetch(`flyctl volumes list -a ${name} -j`).then(({stdout}) => JSON.parse(stdout));
 | 
			
		||||
const appDeploy = (name, appRoot) => runAction(`flyctl deploy ${appRoot} --remote-only --region=ewr`, {shell: true, stdio: 'inherit'});
 | 
			
		||||
const appDeploy = (name, appRoot) => runAction(`flyctl deploy ${appRoot} --remote-only --region=ewr --vm-memory 1024`,
 | 
			
		||||
  {shell: true, stdio: 'inherit'});
 | 
			
		||||
 | 
			
		||||
async function appDestroy(name) {
 | 
			
		||||
  await runAction(`flyctl apps destroy ${name} -y`);
 | 
			
		||||
 | 
			
		||||
		Loading…
	
		Reference in New Issue
	
	Block a user