Open johhansantana opened 7 years ago
under the /lib directory
i couldnt see this updated today in the readme doc. quite useful info for someone just getting started...
inadequate documentation is generally an with software issue. why come to the issue queue to answer basic config questions?
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...
@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 @Fotso https://github.com/yogiben/meteor-admin/issues/384#issuecomment-299458050
create a lib directory at root of your project and create a file AdminConfig.js
with
AdminConfig =
{
adminEmails: ['admin@website.com'],
collections:
{
Posts: {}
}
};
inside.
From https://github.com/yogiben/meteor-admin/issues/77#issuecomment-70686682 :
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: ['admin@website.com'],
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()...).
It's said that you need to add it both in client and server side, but where do I add this configuration?