Reference a settings variable in html head

jjmg · February 28, 2019, 12:32pm

I hope the question explains all, I am new to meteor and I am trying to get one-signal to manage notifications. It is required that I set the below code in the head, I have placed it in a layout.html. I am coming from a very different code background to meteor so im not sure what would even be best practice.
valueFromSettings is the value I need to access from settings, its hard coded right now and one signal is working fine

  <script>
   var OneSignal = window.OneSignal || [];
   OneSignal.push(["init",{
     appId: "valueFromSettings",
   }]);
  </script>

coagmano · March 1, 2019, 12:33am

Usually things like this go into a settings.json file which you load in dev with meteor --settings settings.json or in an ENV var in production

Client settings need to be children of a public key of the json:

{
  "public": {
    "oneSignalAppId": "example"
  }
}

Which you can read with:

Meteor.settings.public.oneSignalAppId;

rjdavid · March 1, 2019, 2:45am

If you really need to place it at the head of the html output, you will also need to check some undocumented functions

WebAppInternals.registerBoilerplateDataCallback can do what you want. Here is the code on how it works:

github.com

meteor/meteor/blob/devel/packages/webapp/webapp_server.js

import assert from "assert";
import { readFileSync } from "fs";
import { createServer } from "http";
import {
  join as pathJoin,
  dirname as pathDirname,
} from "path";
import { parse as parseUrl } from "url";
import { createHash } from "crypto";
import { connect } from "./connect.js";
import compress from "compression";
import cookieParser from "cookie-parser";
import query from "qs-middleware";
import parseRequest from "parseurl";
import basicAuth from "basic-auth-connect";
import { lookup as lookupUserAgent } from "useragent";
import {
  isModern,
  calculateHashOfMinimumVersions,
} from "meteor/modern-browsers";

This file has been truncated. show original

jjmg · March 1, 2019, 12:47pm

Hi @coagmano, thank you for your reply. I wish this was all I needed to get things going but the meteor code just does not work, I do have a settings file that works most places but my code runs inside a in the , this mean that I cannot reference it straight.

jjmg · March 1, 2019, 12:56pm

I am looking at that code now @rjdavid I was wondering what the alternative to placing the code in the head, one signal insist it be done in the documentation, but does it being within a prevent it being of any use anywhere else(as far as letting the see the settings.