under the /lib directory
#384

from meteor-admin.

i couldnt see this updated today in the readme doc. quite useful info for someone just getting started...

from meteor-admin.

inadequate documentation is generally an with software issue. why come to the issue queue to answer basic config questions?

from meteor-admin.

why waste peoples valuable time with poorly documented software? based on the arrogant response and combined poor documentation i'm not going to bother testing this software further. what if i hit a more complex problem? more of the same? no thanks...

from meteor-admin.

@laurencefass I fully understand your disappointment, i also faced the same problem and i have now a bad feeling to this project.
Did you find any alternative way to implement a meteor admin frontend ?

from meteor-admin.

option 1

from @Fotso #384 (comment)

create a lib directory at root of your project and create a file AdminConfig.js with

AdminConfig =
{
	adminEmails: ['[email protected]'], 
	collections:
	{
			Posts: {}
	}
};

inside.

option 2

From #77 (comment) :

in main/server.js : global.AdminConfig = AdminConfig;
in main /client.js : window.AdminConfig = AdminConfig;

And AdminConfig can be defined in a shared/config.js :

export const AdminConfig =
{
	adminEmails: ['[email protected]'], 
	collections:
	{
			Posts: {}
	}
};

and imported like so (in main.js server and client) : import { AdminConfig } from '/shared/config.js';

Note : I used server, client and shared folders because it is the structure of my app but it can be done differently (using Meteor.isClient()...).

from meteor-admin.